home *** CD-ROM | disk | FTP | other *** search
- Path: news.infi.net!usenet
- From: nngis@norfolk.infi.net (Greg DiGiorgio)
- Newsgroups: comp.lang.c
- Subject: Re: Linking Borland and Microsoft .obj
- Date: 24 Feb 1996 20:31:14 GMT
- Organization: Customer of InfiNet
- Message-ID: <4gnsii$i41@nw002.infi.net>
- References: <Dn94E7.A0E.0.bloor@torfree.net>
- NNTP-Posting-Host: h-talisman.norfolk.infi.net
- Mime-Version: 1.0
- X-Newsreader: WinVN 0.99.3
-
- In article <Dn94E7.A0E.0.bloor@torfree.net>, af798@torfree.net says...
- >
- >I have problems with linking a MS object file with Borland program using
- >Borland C/C++ IDE.
- >
- >How to tell IDE linker to take MS library e.g. MLIBCE.LIB. Including it
- >in the project does not work.
- >
- >Using command line TLINK causes problems, too. Reports errors: Undefined
- >symbol __end, __data.
-
- You are playing with fire trying to do this. It's not only that .OBJ
- formats are incompatible, but so are internal function names, system
- variables, and memory management.
-
- I have done something similar to this using Clipper and Turbo-C. Well,
- Turbo-C defined a couple of symbols like you refer to above (_end, _data)
- and the Clipper linker complained with warning messages. The programs ran
- fine however because I knew that the unresolved symbols in my Turbo-C obj
- files would never be called (NCAL). But everytime I recompiled and linked
- I had to ignore those warnings (whihc I'd rather not do). I alos managed
- to get Turbo-C to work with Realia COBOL, but had the same unresolved
- symbol msgs.
-
- But you have to put up with unresolved error/warning msgs if you plan to
- do mixed language/manufacturer programming.
-
- Sorry, I wish I had better news, but I don't.
-
- Hope this helps,
- Greg DiGiorgio
-
-